System and method for modular customization of intermediate business documentation generation

ABSTRACT

Systems and methods capable of providing customized business processes, such as with regard to intermediate business transaction documents, within a standard business process flow system. The systems and methods may include a process interface for receiving the standard business process flow; a developmental graphical user interface capable of developing a plurality of object-oriented custom modules indicative of a plurality of custom business steps; a plurality of data libraries capable of storing at least configurations and rules applicable to the plurality of object-oriented custom modules; a run time graphical user interface capable of selecting multiple ones of the plurality of object-oriented custom modules for inclusion in a custom process stack; and a trigger sensor capable of receiving a trigger indicated by one of the configurations at the process interface, and capable of diverting the standard business process flow to process the custom process stack related to the trigger according to the configurations and rules upon receipt of the trigger.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority to U.S. application Ser.No. 14/680,650, filed Apr. 7, 2015, entitled System and Method forModular Customization of Intermediate Business Documentation Generation,the entirety of which is incorporated herein by reference.

BACKGROUND Field of the Disclosure

The present disclosure relates to generation of custom businessdocumentation, and, more particularly, to systems and methods formodular customization of intermediate business documentation generation.

Background of the Disclosure

It is known to provide business process software to allow forenterprises to streamline and expedite the performance of variousbusiness processes, such as generation of a purchase order, a receipt,or the like. This is particularly the case for businesses that engagein, for example, e-commerce. However, it is also typical that it isexceedingly difficult to deviate from the defined processes madeavailable in such business process software. That is, custom businessprocesses are very difficult to design and implement using knownbusiness process software for the enterprise, unless, of course, one isa highly skilled programmer.

This is generally the case because known business process systemsprovide a variety of algorithmically designed business processes, andany deviation from the provided business processes requires codecustomization. More particularly, custom business processes generallynecessitate the writing and implementation, within the enterprisebusiness software, of specific and unique code to implement the custombusiness process. Although this custom code may be of any known form, itgenerally must be written by one well versed in the writing of computercode, and it must readily interface with the business process softwareused by the enterprise.

A standard business process flow may be provided using, by way ofnon-limiting example, the SAP® business process system (the “SAPsystem”). In the SAP system, an “IDoc,” or intermediate document, is astandard data structure for electronic data interchange (EDI) betweenapplication programs written for the SAP business system, or between anSAP application and an external program. IDocs are used for asynchronoustransactions in which each IDoc comprises a self-contained text filethat can then be transmitted to the requesting workstation withoutconnecting to the central database.

In the SAP “standard flow”, modification to, or to the treatment of, anIDoc, i.e., modification to the text of an IDoc or the process to whichit is subject from standard processes, necessitates code customization.That is, a custom business process requires expert custom coding tocreate the custom process within the SAP standard flow. This isnecessary for each instance of a custom process—meaning that, even if asimilar customization has been provided in a different standard processflow, the coding must be performed anew each time the custom processmust be inserted to a different standard process flow.

Therefore, the need exists for a more suitable system and method forproviding a custom documentation-based business process within knownstandard flow business process systems, without need of codecustomization to provide the custom business process in each case.

SUMMARY OF THE DISCLOSURE

The disclosed exemplary embodiments include systems and methods capableof providing customized business processes, such as with regard tointermediate business transaction documents, within a standard businessprocess flow system. The systems and methods may include a processinterface for receiving the standard business process flow; adevelopmental graphical user interface capable of developing a pluralityof object-oriented custom modules indicative of a plurality of custombusiness steps; a plurality of data libraries, wherein at least one ofthe plurality of data libraries is at least semi-private and at leastone is semi-public, capable of storing at least configurations and rulesapplicable to the plurality of object-oriented custom modules; a runtime graphical user interface capable of selecting, via a drag and dropinterface, multiple ones of the plurality of object-oriented custommodules for inclusion in a custom process stack; a trigger sensorcapable of receiving a trigger indicated by one of the configurations atthe process interface, and capable of diverting the standard businessprocess flow to process the custom process stack related to the triggeraccording to the configurations and rules upon receipt of the trigger;and a return interface that returns an output of the custom processstack to the standard business process flow.

The exemplary systems and methods may additionally include: anadministrator graphical user interface capable of modifying at least oneof the process interface and the return interface; a reporting interfacecapable of providing at least status of at least the standard businessprocess flow and the custom process stack; and/or a partner interfacecapable of providing data regarding at least the custom process stack toone or more partners indicated by at least one of the rules.

Accordingly, the disclosure provides systems and methods for providing acustom documentation-based business process within known standard flowbusiness process systems, without need of code customization to providethe custom business process in each case.

BRIEF DESCRIPTION OF THE FIGURES

Understanding of the present disclosure will be facilitated byconsideration of the following detailed description taken in conjunctionwith the accompanying drawings, in which like numerals refer to likeparts, and wherein:

FIG. 1 is an architectural diagram illustrating a core engine andhierarchy based thereon in exemplary embodiments;

FIG. 2 is a flow diagram illustrating an exemplary custom processaccording to an exemplary embodiment;

FIG. 3 is a flow diagram illustrating an exemplary inbound APIembodiment;

FIG. 4 is a flow diagram illustrating an exemplary outbound APIembodiment;

FIG. 5 is a flow diagram illustrating the replacement of middleware inan exemplary embodiment of the architecture of FIG. 1;

FIG. 6 is a flow diagram illustrating the replacement of middleware inan exemplary embodiment of the architecture of FIG. 1;

FIG. 7 is an illustration of a GUI according to an exemplary embodiment;

FIG. 8 is an illustration of a GUI according to an exemplary embodiment;

FIG. 9 is an illustration of a GUI according to an exemplary embodiment;

FIG. 10 is an illustration of a GUI according to an exemplaryembodiment;

FIG. 11 is an illustration of a GUI according to an exemplaryembodiment;

FIG. 12 is an illustration of a GUI according to an exemplaryembodiment;

FIG. 13 is an illustration of a GUI according to an exemplaryembodiment;

FIG. 14 is an illustration of a GUI according to an exemplaryembodiment;

FIG. 15 is an illustration of a GUI according to an exemplaryembodiment;

FIG. 16 is an illustration of a GUI according to an exemplaryembodiment;

FIG. 17 is an illustration of a GUI according to an exemplaryembodiment;

FIG. 18 is an illustration of a GUI according to an exemplaryembodiment;

FIG. 19 is an illustration of a GUI according to an exemplaryembodiment;

FIG. 20 is an illustration of a GUI according to an exemplaryembodiment;

FIG. 21 is a flow diagram illustrating a re-route from a standardprocess to and through a custom process, according to an exemplaryembodiment;

FIG. 22 is a flow diagram illustrating a re-route from a standardprocess to and through a custom process, according to an exemplaryembodiment;

FIG. 23 is a flow diagram illustrating a re-route from a standardprocess to and through a custom process, according to an exemplaryembodiment;

FIG. 24 is a flow diagram illustrating an exemplary custom processaccording to an exemplary embodiment; and

FIG. 25 is a flow diagram illustrating an exemplary custom processaccording to an exemplary embodiment.

DETAILED DESCRIPTION OF THE EMBODIMENTS

It is to be understood that the figures and descriptions of the presentdisclosure have been simplified to illustrate elements that are relevantfor a clear understanding of the disclosed exemplary embodiments, whileeliminating, for the purpose of clarity, many other elements found intypical similar systems, processes, and modules. Those of ordinary skillin the art may thus recognize that other elements and/or steps aredesirable and/or required in implementing the examples of the presentdisclosure. However, because such elements and steps are well known inthe art, and because they do not facilitate a better understanding ofthe disclosure, a discussion of such elements and steps is not providedherein. The disclosure herein is nevertheless directed to all suchvariations and modifications to such elements and methods known to thoseskilled in the art.

The disclosed embodiments allow for deviation from “prepackaged”intermediate document-centric business processes typically madeavailable in known enterprise business process software. This deviationis preferably available without necessitating the implementer of acustom business process to develop customized code to perform the custombusiness process, and particularly without necessitating codecustomization in each case in which a deviation from a standard flow isneeded—even if the same customization was already coded in anotherstandard process flow. Rather, the disclosed embodiments use objectoriented techniques to allow for the development, definition, andimplementation of a custom business process via a custom process stack.

The custom process stack may be built by selecting modules, wherein theselectable modules may include previously developed elements for othercustom business processes, and as such wherein the modules may be reusedacross multiple customers, multiple custom processes, and the like.Accordingly, the disclosed exemplary embodiments allow for theimplementation of heretofore unknown custom processes, as well as theimplementation of known custom processes in standard process flowsystems in which such custom processes were previously unavailable withundue effort and experimentation.

Based on the selectability of modules, users may recycle modulesdeveloped for/implemented in one business process for use in a differentbusiness process. The implementation of a custom process stack usingobject oriented techniques also allows the disclosed embodiments toprovide simplified graphical user interfaces (GUIs), also referred toherein as “dashboards,” at various process levels, which process levelsmay include administrative, developmental, and process execution phases,in which known techniques of module programming selection, such as “dragand drop” of blocks indicative of modules, may be instituted in, forexample, web-based or app-centric formats.

Within the standard enterprise business software environment known tothe skilled artisan, the disclosed embodiments may reroute the businessprocess software out of its standard process flow to a custom processstack, if the custom process stack is called based on its respectivetriggering criteria. The calling of a custom process stack may beginwith the design/development of a unique process stack, the design of apartially unique process stack, or the processing of a developed customstack. Following the design and/or processing of the custom stack, thedisclosed embodiments may return route from the custom process to thestandard process flow of the base module or modules of the standardenterprise business process software environment.

An enterprise architecture to implement a core engine that may providethe disclosed functionality as extensions of the core engine may besegmented into four layers, namely presentation, business logic, datalogic, and communications/routing. The core engine may provideconfigurable interfaces, i.e., the aforementioned GUIs/dashboards, torecognize, handle, and/or design various stacks, relationships withvarious internal and external entities, and various message and datatypes. The configuration of each such interface, and of stacks designedor implemented therein, and of the modules and module steps of thestacks, may be stored locally or remotely, such as in one or morelibraries, and may include configuration settings based on stack,module, partner, message, or data type, by way of non-limiting example.

The disclosed architecture may provide tools that allow integration ofthe core engine with any of various known types of standard businessprocess systems, such as those offered by SAP® as discussed above, andthose not offered by SAP. As such, the disclosed embodiments may providemulti-platform custom process flow system embodiments, even wherespecific exemplary standard process platforms and systems, such as thatof SAP, are discussed in exemplary embodiments detailed herein. Theaforementioned integration with standard process flow systems may allowfor: modification of documents, intermediate documents, or other datarelevant to business processes, which modifications are then re-postedfrom the custom flow to the standard flow after modification; alerts(such as via email or in-app) in the event of errors in a custom flow;status and reporting for both custom and standard flow; and the like.

In a particular exemplary embodiment, a custom process stack may beintegrated with a standard process flow to, for example, handle errorsand allow managed message re-processing. Such custom stacks may includemodules to: generate alert notifications during communication andmessage processing failures; generate alert notifications for messagesas required by business rules; and/or resubmit failed messages toprocess again.

Similarly, a custom process may be provided to indicate the triggeringcircumstances for, define a configuration of, define style and formatfor, and generate custom internal and/or partner notifications relatedto, a custom business process that generates data, such asdocumentation. Such a custom process may, for example, utilizedistribution lists and/or partner contact information, and may buildnotification messages based on configurable, custom workflows specificto such a distribution list or business partner. These configurable,custom workflows may monitor work flows, and may correspondingly sendalerts to operations and support based on the monitoring.

For each hierarchical level within the enterprise architecture mentionedabove, a management, development, and/or configuration graphical userinterface (GUI), or dashboard, may be provided. The GUI may, forexample, be consistently or differentially provided on a mobile orstationary computing devices. The GUI may allow for the creation,display, causation, update, and/or deletion of aspects of data, such asaspects of an IDoc, uniquely for each message data type and/orrecipient. Thereby, message data and data generally may be distinct asbetween internal and external personnel, and/or may be unique or genericto particular external persons or across multiple or all externalpersons.

Yet further, the architecture may allow, such as via the afore-discussedGUI, the display of the monitoring of and reporting on operationalmetrics and errors, by way of non-limiting example. This additionallyallows for the logging of data for standard and custom message flows anderrors, and the providing of reports on status, such as message statusupdates.

The enterprise architecture 100 may be illustratively defined using aconcentric hierarchy diagram, as shown in FIG. 1. As shown in FIG. 1,the core engine may provide the basis for the customization ofprocesses. The core engine 102 should not be modified except in therarest of circumstances, and at that only by highly expertadministrative personnel, as modification to the core engine impacts theentire architecture and all modules, stacks, and libraries therewithin.Accordingly, an administrative dashboard 102 a may be provided foraccess to core functionality exclusively by high level administrative,or “super,” users. The administrative dashboard 102 a may compriseadministrative elements of corporate process functionality, and/oradministrative elements related to custom stack modules and theinterface thereof with standard flows.

Illustratively “around” the core engine and administrative functionalitymay be provided an “internal” development zone 104, in which is providedthe development dashboard 104 a discussed herein throughout. Thedevelopment zone 104 allows for development of various custom stackmodules, to which are applied the configuration definitions and rulesthat form the libraries in the library zone about the internaldevelopment zone. In this zone 104, for example, and object class may beprovided to perform purchase order duplication checks on a sales orderprocess. It is this developmental portion 104 of the hierarchy thatallows for the locating, adaption, or development of new modules forinclusion in custom stacks.

Illustratively “around” the libraries of rules and configurations forthe developed modules, and the developed modules themselves, may beprovided the run time zone 106. In the run time zone 106, a user mayformulate a stack of modules from the development zone 104, subject tothe definitions of the library zone. Access to the modules, i.e., viasearch, request, selection, or otherwise, may also be defined in the runtime zone for providing in the run time dashboard 106 a. The run timedashboard 106 a subjects selected modules to configuration elements,such as JAVA and mobile elements, which implement rules to allow forperformance of that module uniquely within a custom stack.

The run time dashboard 106 a accessibility to the modules provided fromthe development dashboard 104 a may be provided to users in any formknown in the art, such as a guided process, a wizard 108, or the like.That is, a user may be asked a series of questions from which a limitedsubset of models may be selected or made available for selection toallow the user to implement the desired custom process, and/or the usermay be provided with search capabilities, drop-down menus, hierarchies,file selections, or the like that may allow the user to actively seekout selection of module or modules that the user believes may bestimplement a desired custom process. As referenced, the run time buildprocess may be visually performed in a manner indicative of the objectoriented nature of the disclosed embodiments—meaning the user may select“block” modules and drag and drop those modules in a position orpositions, and/or in any particular order, to best effectuate the user'sdesired custom process.

More particularly, because custom stacks may often use similarfunctions/stack modules, a custom stack configuration wizard maygenerate custom stacks using existing modules when possible. The wizardmay use metadata from the module attributes to supply user-friendlyinformation for the in-dashboard wizard. The wizard may select theseexisting stacks and stack modules either as partner-specific options, orpartner-agnostically, such as from an internal library, a remote, globallibrary, or preferentially in a given order from these or other librarysources.

In addition, such a wizard may provide, both in the development and runtime dashboards, standard templates to develop, and to structure andrun, message stacks. Templates represent default business processes thatcan be used as is, or copied and customized in the development zone.These templates allow for the development and execution of custombusiness processes. Further, multiple modules may be enabled forinclusion into a stack by selecting a single template.

The wizard may accordingly comprehend different message types and howthey are used by different business objects, so features associated withthese different message types may be correctly grouped and searched. Thegrouping may be done by identifying which message types act on variousbusiness objects in the standard flow. That is, it may be determinedwhich business object is used by the message type, such as by reviewingthe list of valid message types per business object. If a new messagetype is needed, the necessary configuration may be built in a libraryaccessible to the wizard to tie the subject business object and themessage type together.

Correspondingly, the transaction associated with the display of thebusiness object, and confirmation that the correct transaction will bedisplayed by the runtime dashboard, may occur. The features that areavailable for the message type/business object may then be displayed,and the user may be allowed to select the desired features, includingany custom aspects and associated notes or administrative entitlements.

If a stack already exists for the desired features, the wizard mayidentify it for use, such as responsive to a search, and may provideinformation associated with any module, such as attached documents, usermanuals or the like, prior use records, frequently associated errors,and so on. If a stack does not already exist for the desired features,but the modules exist to build it, the wizard may create the necessarymessage stack. If a stack does not already exist and at least some ofthe modules do not exist to build it, either the user may be allowed toaccess the development dashboard, or the user may enter a description ofthe needed functionality for a developer in the development dashboard.

Among myriad other functionality, the wizard may allow for users todetermine where a specific custom module is or may be used. For example,a user may be working on a custom process for customer XYZ. The wizardmay allow the user to search for customer XYZ in the stack module nameor other associations in any one or more libraries administrativelyaccessible to that user, in order that the user may re-use customprocesses previously developed for customer XYZ.

The wizard may thus identify an existing message stack or create a newmessage stack; create a new workflow, partner, and/or organizationalunit, or identify an existing one; create a new workflow responsibilityor identify an existing one, and assign users to that responsibility;create or update a partner profile, message profile, or data profile;and configure rules, configurations, or data/message types, and assignfeatures, data and modules to libraries. The wizard may allow forsearching through the foregoing, and/or interaction with developersthereof, or development by the user thereof.

In accordance with the disclosed embodiments, various processes may bemade available via the run time dashboard 104 a, such as for inclusionin a custom process using the disclosed wizard. For example, error-basedcustom processes may determine the proper actor responsive to givenerrors. In the exemplary embodiment of FIG. 2, multiple error paths 202,204, 206, 208, 210, 212, 214 may be explored concurrently in a genericerror notification and alert outbound flow. In the illustration, whenerrors occur during execution of an outbound module stack, e-mailnotification of the error may be sent to the users in the organizationalstructure identified by a particular value in the company field in theoutbound parameters of the partner profile. This field may also be usedin inbound processing for determining the users responsible for errorhandling.

In the illustration, an error occurs or may occur in that a document maybe requested that does not exist. In prior methodologies, a genericerror message may be provided in such a circumstance. However, in thedisclosed embodiments, the run time dashboard may allow forimplementation of a variety of decision modules in a particular orderthat should be performed in the event of an error. As such, the decisionbranches make the options selected by the user and the run timedashboard. Consequently, in the disclosed embodiments and contrary tothe known art, the user that caused the error, or another user asindicated by the custom process, may be presented with a series ofoptions and or selections to cure the error based on selected customprocess functionality, but the user may preferably never exposed to theunderlying error work flow code (although a developer at the developerdashboard may or may not wish to access code when structuring the customerror process).

In an additional example, post processing is frequently provided in theknown art. In the known art, such a process is solely implemented post,i.e., following, a given process. However, the disclosed embodimentsallow for a user at the run time dashboard to drag a series of modulesinto a custom post processing stack that allows for a variety offunctionality to be carried out after a sales order is created, i.e.,post-sales order process, without any need of the implementer of thecustom process to do additional coding beyond that which is alreadyprovided in the custom stack modules and the standard process flow.

Returning now to FIG. 1, encompassing the internal run time zone is thepartner interface zone 110. It is via this zone 110, such as using apartner interface dashboard 100 a, that access to various functionality,as defined in the libraries, may be provided to one or moretransactional, external business partners. For example, only processstacks having modules developed specifically for accessibility to aspecific partner may be accessible via this zone. Thereby, this may bean “externally facing” zone, such as may be used to provide an objectclass to perform data transformations specific to a particular customer.

More specifically with respect to the hierarchical illustration of FIG.1, in the custom stack library, reusable, object oriented blocks thathave been created in the development zone 104 are stored, in conjunctionwith corresponding configurations and rules. The custom stack librarymay preferably be searchable to users, such as via the run timedashboard 106 a, wherein the search ability may be provided by rulesdefined in the development zone and stored in the library.

That is, a user may be able to search the libraries for object orientedmodules in the category of “sales”, for example, or in any othercategory, of use to that particular user. Moreover, the user may be ableto search for and find only internal modules, or global library modulesprovided across numerous enterprises. The search configuration may thushave a generic aspect to allow for use across libraries subject tovarious different configurations or rules, such as allowing for typingof free form text into a search window when seeking custom objectoriented modules. Thereby, a user may avoid having to recreate objectmodules that have previously been created, either for the same purposethe user intends to use the module in a current instance, or that havebeen created for a different reason and placed within the custom stacklibrary.

Moreover, the custom stack library includes the referenced configurationrules that indicate when certain custom stacks are to be run, and how.The manner in which a stack executes may vary based on the configurationrules stored in one or more stack libraries, which libraries may beprivate and limited (such as for a subset of personnel within acompany), private within a company, semi-public (available outside ofthe company to limited partners), or public. This is distinctly contraryto the known art, in which the lack of a library necessitates theaddition of custom code for each custom process each time the customprocess must be used. That is, customized modules cannot be recycled indifferent process stacks in the known art. Accordingly, up to 90% of thecoding required in known business process software to allow forvariation from standard flows may be avoided in the disclosedembodiments due to the reusable nature of the object oriented elementsmade available for a custom process stack. Moreover, the code librarymay additionally include necessary interface “hooks” to allow forinterfacing of the custom stack with the standard flow across variousbusiness process system platforms. The standard flow may include, forexample, processing of a sale order, generation of a purchase order, orthe like. And deviations may include, for example, modification of atypical purchase order for a particular new customer.

One or more application programming interfaces (APIs) may be provided toinitiate the core engine to process stacks and/or set up custom stacksvia the development dashboard. The core engine may include interfacingto “plug-in” to a standard process flow engine 302, 402 that executes anembedded standard flow process, which “exits” the process from thestandard flow to the custom process 304, 404, which allows theprocessing of the custom stack modules 306, 406 indicated to complete agiven custom business process, and which then returns the process to thestandard flow 308, 408. Thereby, the selected custom process deviatesfrom the standard flow processing by executing the plug-in core toperform the custom stack modules prior to returning to the standardprocess flow.

The aforementioned API or APIs may allow for development of processesthat initiate the core engine for respective inbound or outboundprocesses. Inbound process, as used herein, may include, for example,when a customer sends data/code through a standard process flow to theimplementer, and the implementer processes that data/code through acustom stack at the direction of the core engine of implementer.Outbound process, as used herein, may include sending data/code outputby the custom stack of the implementer to the customer.

Once initiated to run time, the core engine runs the custom stackmodules, which in turn executes the underlying business logic defined bythe developer for that process in the library. An inbound custom processflow is illustrated in FIG. 3. In the illustration, an inbound processis delivered to the core engine, and is subjected to the custom stack.In FIG. 4, an outbound process is delivered to the core engine, whichinitiates the custom stack to execute the outbound custom process.

As referenced, processing of inbound and outbound data messages may beenabled from numerous known standard flow processing systems, and thusmay be enabled from multiple different business partners and/or businesssystems. In a specific exemplary embodiment, although third-partymessage middleware 502 typically must pre-process and map inbound EDImessages into IDocs for SAP business process system consumption, theherein disclosed core engine handles the complex business logic andsimplifies the mapping effort normally performed at 502 for an inboundprocess. More particularly, the core engine may handle non-IDoc inboundmessages by processing a trigger IDoc sends from the middleware 502after the middleware saves the inbound message data in a configuredinbound location; partner and message-specific modules may then convertthe non-IDoc message into business information and automate theassociated business process. This is shown in the exemplary embodimentof FIG. 5. Thereby, the core engine allows configuration of custommessage-handling stacks that can be linked to any number of customers,vendors, libraries, or the like for each message type.

With regard to outbound processing of messages in a specific exemplaryembodiment, standard SAP process flow and custom triggered eventsgenerate a given SAP output. The core engine may pre-processes IDoc andnon-IDoc SAP outputs before delivering them to the middleware 602 ordirectly to a non-SAP system, as shown in FIG. 6. Thereby, the coreengine allows configuration of custom message-handling stacks that canbe linked to any number of customers, vendors, libraries, or the likefor each message type.

As discussed above, a developer dashboard provided by and integratedwith the core engine may be used for registering new custom stackmodules, and for making those custom stack modules available for“external” custom processing from standard process flow systems. Thedeveloper dashboard may enable one, selected, or all existing customstack modules, such as for a particular entity or for placement into apublicly available data library, to be made available to standardbusiness process flows. Accordingly, the disclosed embodiments mayprovide reusability of custom stack modules from within the core engine.

Different custom business processes may be registered, and associatedwith libraries and configurations and/or subjected to administrationrules, through the developer dashboard, such as to make those customprocess modules available for run time from the core engine. Forexample, each custom module may be registered to one or more libraries,such as an internal company library for developers of “Project A” only,internal libraries for developers of “Project A” and “Project C”, to ancompany internal library open to all developers or to all personnel, orto a public library available to all or select third party users of thedisclosed embodiments. FIG. 7 illustrates an exemplary interface 702 ofthe developer dashboard in which custom modules may be registered.

In addition, the configuration of the modules may include assignment ofthe stack module to one or more particular business processes. Likewise,configuration may include the type of stack, such as inbound or outboundprocesses, step type for modules, naming conventions, circumstancesunder which the stack may be called and by whom, and so on. Step typemay include a definition of actions that will be carried out uponexecution of each module in the stack. Configuration aspects may beentered via a user interface 802 of the developer dashboard such as theone shown in the example of FIG. 8.

A run time configuration dashboard may allow for the configuration ofhow an inbound or outbound custom process, in conjunction with astandard flow, may be processed. The run time configuration dashboardallows the user to specify the stack modules that will be executed, andthe sequence in which the execution will occur. As discussed herein, therun time configuration dashboard may include a guided process and/or awizard. Thereby, the disclosed embodiments may provide assistance inhelping a user select a series of modules and/or stacks to accomplish adesired task, such as by recommending particular modules from the stacklibraries.

Further, a user at the configuration dashboard may copy/reuse one ormore modules, stacks, and/or configurations from within the user'sadministrative environment, i.e., from within the user's company, froman business partner, i.e., a customer or offer or in a given businesstransaction, or from a public library, to meet a current requirement.This reuse may be simplified through the providing of an intelligentsearch capability within the run time configuration dashboard to help auser identify existing stack modules available from the reusable stacklibrary.

An initial input screen 902 for setting up a run time configuration of acustom stack module for specific business partner is shown in FIG. 9. Anexemplary embodiment of an intelligent search 1002 for stacks/modules inthe library of a business partner is shown in FIG. 10.

An exemplary main configuration interface 1102 for the run timeconfiguration dashboard is illustrated in FIGS. 11 and 12, in which theleft pane shows an available stack module for the particular selectedactivity from the stack library, by way of non-limiting example. Stackmodules to be used from the reusable library may be dragged to the rightpane, wherein the right frame may specify the final stack that will beprocessed by core engine for the custom business process.

A runtime dashboard may allow for custom process stack execution, stackerror monitoring and resolution, and custom process reporting. The runtime dashboard may be a web based dashboard.

By way of non-limiting example, the user may have the option to see anerror log for a selected custom process, and/or may arrive at and/orinitiate additional custom steps toward a possible solution to fix theerror. A user at the run time dashboard may also reprocess all or partof the custom process stack from the run time dashboard. If, forexample, the user believes an error is irrelevant, or a new set of datais required, a forced return to the standard process flow may beeffectuated from the run time dashboard. By way of example using the SAPbusiness system, a user who deems that new data needs to be pushed frombusiness partner may close a current IDoc from the custom stack tothereby complete its processing in the SAP standard flow. An exemplaryrun time dashboard interface 1302 is illustrated in FIG. 13. Drill down1402, such as per IDoc, may be available via the run time dashboard, asis shown in the example of FIG. 14.

Of course, the afore-discussed dashboards and all other dashboards andinterfaces discussed herein may not only be provided as web-basedapplications, but likewise may be provided as mobile apps. For example,a runtime dashboard mobile app may provide a simplified version of aweb-app runtime dashboard, such as may be readily executed by iOS orAndroidOS devices. Correspondingly, a user may view errors, IDocs, andthe like through the mobile app.

Likewise, a user may have the option to see detail, such as detailederror logs for analyzing an issue to arrive at possible resolution, inthe mobile app. The use may additionally have reprocess/close capabilityfrom a mobile device.

A mobile app according to the disclosure may have optionality typical ofmobile apps. By way of non-limiting example, a user may elect to receivepush notifications upon occurrence of any IDoc error in system that hasbeen processed through a custom process of the core engine.

In a mobile app context, the user may be provided with a landing page,which may show key information for run time, such as all error itemsassigned to that user. An exemplary landing page 1502 for a mobile appis shown in the example of FIG. 15. Upon tapping any item on the landingpage of FIG. 15, a detailed error screen 1602, such as that shown inFIG. 16, may be displayed along with other critical pieces of data. Asindicated by the exemplary interface screen shot 1702 of FIG. 17, followup actions for critical items may be displayed, such as in an overlayicon set and/or when a user swipes, such as from right to left.

Upon clicking any of the follow up actions shown in FIG. 17, aconfirmation pop up 1802 may appear as shown in the illustration of FIG.18. As shown in FIG. 19, an indication of the success or failure of auser action 1902 may additionally be provided in the mobile app.

Additional optionality, such as additional run time filter criteria, maybe provided in the typical manner for a mobile app. For example, a swipeto the left, or execution of a drop down, may cause to be provided anavigation pane on screen side left. Moreover, an inbox, such as withmessages relating to actions to be taken, such as in the case of errorsin custom process flows, may be selectable in the app via any knownmethodology. The foregoing is illustrated in the screen shot 2002 ofFIG. 20.

FIG. 21 illustrates an exemplary process flow 2100. In the illustration,an inbound or outbound standard process experiences a deviation based,in this example, on a custom process that is uniquely carried out for aparticular business partner, as is indicated to the core engine by aprocess code associated with that business partner. The custom processincludes structuring the indicated custom stack based on that customprocess for that partner. If the custom stack or aspects thereof cannotbe located 2102 or are improperly called, an error message is produced2106. If the custom stack is properly called, structured and available,it is run 2108, and thereafter the core engine returns the process tothe standard flow 2110.

FIG. 22 is an exemplary process flow 2200 associated with the disclosedembodiments. More particularly, FIG. 22 illustrates the location of acustom stack, and the strings, rules, and configurations associatedtherewith, referenced generally with respect to the foregoing figure. InFIG. 22, the exemplary process flow seeks the settings 2202 andclassification 2204 a, 2204 b for a particular partner, message, ortype. If a unique custom stack is found 2210, it may be initiated to runtime by step 2212. If a dedicated custom stack is not found 2214, but ifthere is a standard custom stack 2208 for, for example, a partner of thetype assessed, that standard custom stack may be initiated to run time.If no custom or standard stack is located for the particular partner,message, or type, a global custom stack 2209 may be initiated to runtime at step 2212. If the partner, message, or type does not fit withinany classification or configuration that would necessitate a customstack, no custom stack is initiated and the process is returned to thestandard flow.

FIG. 23 is a flow diagram illustrating an exemplary flow of theprocessing of a custom stack at run time 2300. In the illustration, theexecution of the custom stack may vary as to whether the process relatesto multiple, or “mass”, steps 2302, such as may relate to multipleIDocs, or to a single step 2304, such as may relate to a single IDoc,message, or data point. In either case, pre-processing modules of thecustom stack are executed 2306, followed by before processing modules2308, followed by in-processing modules 2310, 2310 a-b. Of course,post-processing modules 2312 may also be executed if pre-, before-, andin-processing modules run error free. If errors do occur, they may betreated in accordance with the custom stack modules. Data, such asIDocs, are updated according to the processing, and the foregoing stepsare repeated for additional documents in a mass execution.

FIG. 24 illustrates an exemplary flow for a particular process in thedisclosed systems. In the illustration, an inbound notification handlercustom workflow 2402 is shown for: evaluating an application log and, inthe case of critical messages collected, triggering an event(EPICErrorOccured) to start the an inbound error handling workflow(WS91000020); otherwise analyzing the application log; analyzing IDocdetails; re-processing an IDoc if needed (such as in the event of anerror); deletion of an IDoc if no longer relevant; and, in case that theprocessing stack contains “Special Error Handling” modules, triggeringan event referenced as “INBOUNDERROR” for particular data classes, whichin this particular example is data class ZCL_EPCB_CTL_IDOC_PPWRKFLW. Ofnote in this example, each workflow task or module is assigned a code,to allow for it to be modularly employed outside of the standard flow inother custom stacks in the future. For example, tasks include:TS91000062—Create PP Workflow Object Ref; TS91000056—Execute PostProcessing Module; TS91000060—Exceptions while Processing EPIC ErrorHandling Module; TS91000057—Display Application Log;TS91000063—Determine DeadLine; TS91000054—User Decision: IDoc ErrorHandling; TS91000041—(Re)-Process IDoc; TS91000042—Refresh IDocAttributes; TS91000043—Delete IDoc; TS91000042—Refresh IDoc Attributes;TS91000039—Display Application Log; TS91000044—Display IDoc Details; andTS91000064—Deadline Date Missed. Of note, any variable definitions,names, configurations, or subject rules disclosed herein throughout aresolely exemplary and non-limiting in nature.

FIG. 25 illustrates an exemplary embodiment of the execution of a postprocessing manager custom stack 2502. In the illustration, a custom postprocessing workflow is triggered asynchronously (by means of functionmodule Z_EPCB_EVENT_RAISE_INUPD) in custom stack modules if the custompost processing is defined (by method module EVA_PROCESS_STACK) and ifthere were no critical errors previously reported.

In the example of FIG. 25, workflow task TS91000056 will carry out allpost processing using underlying class method PROCESS_MODULE. In case ofan error exception, the workitem will be assigned to a group of usersmaintained under workflow rule 91000004 (Rule: Message/Partner/Plant).This processing will continue to a loop until any error is resolved oruntil the process is explicitly closed by a user.

Thus, the disclosed exemplary embodiments improve existing functionalityof standard process flow business software, such as by supplementingexisting standard process functionality to address gaps in, for example,IDoc and EDI communications. Moreover, the disclosed embodiments mayprovide an enterprise architecture that follows a uniform design toensure that a core engine processes all messages and generates alertswhen actionable events (errors and process notifications) occur.Further, the disclosed embodiments support a wide range of businessprocesses and message types using configurable “plug-and-play” moduleelements.

The various illustrative logical blocks, modules, algorithms and virtualcircuits described in connection with the disclosure herein may beimplemented or performed with a general-purpose processor, a digitalsignal processor (DSP), an application specific integrated circuit(ASIC), a field programmable gate array (FPGA), or any otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described herein. A general-purpose processor may be amicroprocessor, but in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of computing devices,e.g., a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration.

The steps of a method, display, or algorithm described in connectionwith the disclosure herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. Anexemplary storage medium is coupled to the processor such that theprocessor can read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anASIC. The ASIC may reside in a user terminal. In the alternative, theprocessor and the storage medium may reside as discrete components in auser terminal.

In one or more exemplary designs, the functions described may beimplemented in software, wherein the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium, and preferably on a non-transitorycomputer-readable medium. Computer-readable media includes both computerstorage media and communication media including any medium thatfacilitates transfer of a computer program from one place to another,such as over a local or wide area network, a cellular network, asatellite network, or the like. A storage media may be any availablemedia that can be accessed by a general purpose or special purposecomputer. By way of example, and not limitation, such computer-readablemedia can comprise RAM, ROM, EEPROM, CD-ROM or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium that can be used to carry or store desired program codemeans in the form of instructions or data structures and that can beaccessed by a general-purpose or special-purpose computer, or ageneral-purpose or special-purpose processor. Also, any connection isproperly termed a computer-readable medium. For example, if the softwareis transmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, DSL, orwireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer-readable media.

The previous description of the disclosure is provided to enable anyperson skilled in the art to make or use the disclosure. Variousmodifications to the disclosure will be readily apparent to thoseskilled in the art, and the generic principles defined herein may beapplied to other variations without departing from the spirit or scopeof the disclosure. Thus, the disclosure is not intended to be limited tothe examples and designs described herein, but is rather to be accordedthe widest scope consistent with the principles and novel featuresdisclosed herein.

1. A method of providing a customized business process within a standardbusiness process flow system, comprising: receiving the standardbusiness process flow; developing in a developmental graphical userinterface of a plurality of object-oriented custom modules indicative ofa plurality of custom business steps; providing a plurality ofsemi-private data libraries and semi-public data libraries, capable ofstoring at least configurations and rules applicable to the plurality ofobject-oriented custom modules; selecting, via a drag and drop graphicaluser interface, multiple ones of the plurality of object-oriented custommodules for inclusion in a custom process stack; sensing a triggerindicated by at least one of the configurations and the rules; divertingthe standard business process flow to the custom process stack accordingto the configurations and rules upon receipt of the trigger; andreturning an output of the custom process stack to the standard businessprocess flow.
 2. The method of claim 1, wherein the standard businessprocess flow produces an intermediate document, and wherein the outputcomprises a modification to the text of the intermediate document. 3.The method of claim 1, wherein the trigger comprises a business partner.4. The method of claim 1, wherein the trigger comprises a message type.5. The method of claim 1, wherein the trigger comprises an error in thestandard business process flow.
 6. The method of claim 1, wherein onesof the plurality of object-oriented custom modules are re-usable afterentry into at least one of the libraries.
 7. The method of claim 1,wherein the drag and drop graphical user interface is at least partiallycapable of selecting at least a portion of a one of the plurality ofobject-oriented custom modules entered into at least one of thelibraries.
 8. The method of claim 1, wherein the drag and drop graphicaluser interface further comprises a drop-down selection interface.
 9. Themethod of claim 1, wherein the drag and drop graphical user interfacefurther comprises a selectable file tree interface.
 10. The method ofclaim 1, wherein at least one of the developmental graphical userinterface and the drag and drop graphical user interface comprises amobile app interface.
 11. The method of claim 1, further providescomprising providing an administrator graphical user interface.
 12. Themethod of claim 1, wherein at least one of the developmental graphicaluser interface and the drag and drop graphical user interface comprisesa web-based interface.
 13. The method of claim 1, further comprisingproviding a network interface, wherein at least the standard businessprocess flow is received over the network interface.
 14. The method ofclaim 1, wherein the developmental graphical user interface comprises anapplication programming interface (API).
 15. The method of claim 1,wherein the output comprises an alert indicated by a one of theconfigurations to at least one recipient indicated by a one of therules.
 16. The method of claim 15, wherein the alert comprises an email.17. The method of claim 15, wherein the alert comprises an in-appindicator.
 18. The method of claim 1, further comprising: providing areporting interface capable of providing at least status of at least thestandard business process flow and the custom process stack.
 19. Themethod of claim 1, further comprising: providing a partner interfacecapable of providing data regarding at least the custom process stack toone or more partners indicated by at least one of the rules.
 20. Themethod of claim 1, wherein the custom stack at least partially comprisesa portion of the standard business process flow.